System and method for image file generation and management

ABSTRACT

An imaging platform may determine whether an image file stored on a client device is a current version of the image file, and may identify, based on determining that the image file on the client device is not the current version of the image file, the current version of the image file in an image file store. The imaging platform may determine, based on identifying the current version of the image file and based on one or more properties associated with a network connection of the client device, a bandwidth allocation for transmitting the current version of the image file to the client device. The imaging platform may transmit, to the client device, a mapping table associated with the current version of the image file, and may transmit, based on the bandwidth allocation and based on the mapping table, the current version of the image file to the client device.

BACKGROUND

An image file may be used to install an operating system, a softwareapplication, or some other electronic file on a client device. Theclient device may receive the image file from a server, another clientdevice, and/or the like, via a network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1P are diagrams of an example implementation described herein.

FIG. 2 is a diagram of an example mapping table.

FIG. 3 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented.

FIG. 4 is a diagram of example components of one or more devices of FIG.3;

FIG. 5 is a flow chart of an example process for image file generationand management.

FIG. 6 is a flow chart of an example process for image file generationand management.

FIG. 7 is a flow chart of an example process for image file generationand management.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

An information technology (IT) administrator may manage a plurality ofclient devices associated with one or more organizations. Managing aclient device may include installing an operating system (OS) on theclient device, installing one or more software applications on theclient device, troubleshooting an issue associated with the clientdevice (e.g., a networking issue, an OS issue, a software applicationissue, a hardware issue, etc.), repairing the client device (e.g.,reinstalling a software application on the client device, reinstallingan OS on the client device, replacing hardware on the client device,etc.), and/or the like.

In some cases, an IT administrator may remotely install an OS, asoftware application, and/or the like, on the client device over anetwork. To do so, the IT administrator may use a server device, anotherclient device, and/or the like, to transmit an image file to the clientdevice, and transmit an instruction to the client device to install theOS, the software application, and/or the like, on the client device.

An image file may be an electronic file that includes one or moresoftware elements, such as an OS, a software application, a devicedriver, and/or the like. In some implementations, an image file may beused to deploy a client device (e.g., by installing an OS and one ormore applications on the client device for the first time), to updatethe client device, (e.g., by updating the OS and/or the one or moresoftware applications), to repair the client device (e.g., byreinstalling the OS and/or the one or more software applications, byrestoring the OS and/or the one or more software applications to aprevious state, etc.), and/or the like.

In some cases, an image file may be tens of gigabytes in size or more.Due to the image file's large size, transmitting the image file to aclient device over a network may consume significant network resources,which may cause other client devices in the network to experience anincrease in network latency, a degradation in performance ofnetwork-provided services, and/or the like. Moreover, the ITadministrator may have to maintain hundreds of different image files,which may require significant storage resources to store.

Some implementations described herein provide an imaging platformcapable of generating an aggregated image file that includes a pluralityof permutations of an image file. In this way, the imaging platform maystore and maintain hundreds of different permutations of the image filein a single aggregated image file, which reduces the complexity ofstoring and maintaining the plurality of permutations of the image file.Moreover, the imaging platform may deduplicate the plurality ofpermutations of the image file when generating the aggregated image fileso that common portions of the image file between the plurality ofpermutations are stored once in the aggregated image. In this way, theimaging platform reduces the amount of storage resources used to storethe aggregated image file.

In some implementations, the imaging platform may be capable of ensuringthat a client device managed by the imaging platform stores the mostrecent version of an image file by periodically determining whether animage file stored on the client device is a current version of the imagefile, and transmitting the current version of the image file to theclient device based on determining that the image file stored on theclient device is not the current version of the image file. In this way,if the client device experiences a fault and needs to be recovered orrebuilt, the imaging platform may recover or rebuild the client deviceusing the updated version of the image file stored on the client deviceinstead of having to transmit the updated version of the image file tothe client device over a network, which reduces the amount of time ittakes to recover or rebuild the client device, and reduces the amount oftime that the client device is unusable or offline.

In some implementations, the imaging platform may determine anddynamically adjust a bandwidth allocation for transmitting an image fileto a client device over a network based on one or more propertiesassociated with a network connection of the client device. In this way,the imaging platform may transmit the image file to the client device ina way that does not adversely affect the network connection of theclient device and/or network connections of other client devices in thenetwork, which conserves network resources and minimizes network latencyand/or degradation in performance of network-provided services.

Some implementations described herein provide a client device that mayreceive a plurality of portions of an image file from the imagingplatform (or from another location), and may generate a plurality ofintermediate hash values, for the plurality of portions, while theplurality of portions is in a memory on the client device. The clientdevice may transfer the plurality of portions to a storage drive on theclient device, may generate a copy of the image file, and may generate afinal hash value, for the copy of the image file, from the plurality ofintermediate hash values. In this way, the client device may decreasethe amount of time it takes the client device to generate a hash valuefor the copy of the image file by generating the plurality ofintermediate hash values for the plurality of the portions of the imagefile, while the plurality of portions of the image file are in thememory on the client device.

FIGS. 1A-1P are diagrams of an example implementation 100 describedherein. As shown in FIGS. 1A-1P, implementations 100 may include one ormore client devices, a preboot execution environment (PXE) server, animaging platform, and/or the like.

The one or more client devices (e.g., client device 1, client device 2,and/or the like), may be capable of performing one or more actionsassociated with an image file. For example, a client device may requestan image file (e.g., from the imaging platform, from the PXE server,from another client device, and/or the like), receive an image file(e.g., from the imaging platform, from the PXE server, from anotherclient device, and/or the like), transmit an image file (e.g., toanother client device), load and/or install an image file on the clientdevice, and/or the like. In some implementations, the one or more clientdevices may be included in a same subnet, of a plurality of subnets, ona network.

The PXE server may be included in the network on the same subnet as theone or more client devices or another subnet. The PXE server may allowthe imaging platform and/or a client device to remotely transmit, load,and/or install image files on a PXE-enabled client device of the one ormore client devices. A PXE-enabled client device may be a client devicethat includes a network interface component that stores PXE firmwareand/or a unified extensible firmware interface (UEFI) including the PXEfirmware. The PXE firmware allows the PXE-enabled client device toobtain an internet protocol (IP) address using the dynamic hostconfiguration protocol (DHCP) (e.g., from a DHCP server on the PXEserver or another DHCP server on the network) so that the PXE-enabledclient device may access the PXE server on the network. The PXE-enabledclient device may access the PXE server to download an OSpre-installation environment image file from the PXE server, and load anOS pre-installation environment into a memory on the PXE-enabled clientdevice from the OS pre-installation environment image file. The OSpre-installation environment may execute and connect to the PXE server,download an OS image file onto the PXE-enabled client device, andinstall an OS onto the PXE-enabled client device from the OS image file.

The imaging platform may include one or more server devices, such as acloud-based server device, a middle tier server device, a backend serverdevice, and/or the like. The imaging platform may receive image files,generate and maintain image files, store image files, transmit imagefiles to the one or more client devices and/or the PXE server, transmitinstructions to the one or more client devices and/or the PXE server,and/or the like.

Turning now to FIG. 1A, as shown by reference number 102, the imagingplatform may receive an image file and generate an aggregated image filefrom the image file. The aggregated image file may include a pluralityof permutations of the image file. A permutation of the image file mayinclude one or more modifications to the image file, such as one or moreadditional software elements, one or more software elements removed fromthe image file, one or more changes to a software element included inthe image file, and/or the like.

In some implementations, each permutation, of the plurality ofpermutations of the image file, may be associated with an organizationalrole, of a plurality of organizational roles, associated with anorganization. An organizational role may include, for example, asoftware developer role, a financial planner role, a drafter role, asupply chain analyst role, a purchasing role, and/or the like.

An organizational role may be associated with a role configurationstored in a role data store, which may be a data structure such as afile system, a database, a table, a linked-list, a tree, and/or thelike. In some implementations, the role data store may be included inthe imaging platform and/or in another location in the network. The roleconfiguration for the organizational role may include informationidentifying one or more modifications to the image file that are to beincluded in a permutation, of the image file, associated with theorganizational role.

A permutation, of the image file, associated with an organizational rolemay include a set of software elements tailored to the organizationalrole. As an example, a permutation, of the image file, associated withan electrical engineering role may include a schematic design softwareapplication, an electronic circuit simulation software application, aprinted circuit board (PCB) layout software application, and/or thelike. As another example, a permutation, of the image file, associatedwith a project manager role may include a project scheduling softwareapplication, a budget planning software application, a customerrequirements management software application, and/or the like.

As shown by reference number 104, the imaging platform may providecopies of the image file to a plurality of virtual machines on theimaging platform and/or in another location in the network.

Turning now to FIG. 1B, and as shown by reference number 106, theimaging platform may provide a plurality of organizational roles to theplurality of virtual machines. In some implementations, each virtualmachine, of the plurality of virtual machines, may receive a differentorganizational role, of the plurality of organizational roles. Forexample, a virtual machine may receive a graphic designer role, anothervirtual machine may receive a web developer role, and so on.

Turning now to FIG. 1C, and as shown by reference number 108, theplurality of virtual machines may generate a plurality of permutationsof the image file. For example, each virtual machine, of the pluralityof virtual machines, may generate a permutation, of the plurality ofpermutations, of the image file. In some implementations, one or morepermutations, of the plurality of permutations, of the image file may begenerated in parallel. For example, a first virtual machine may generatea first permutation of the image file at a time that overlaps (eitherpartially or fully) a time that a second virtual machine in generating asecond permutation of the image file. In some implementations, theplurality of virtual machines may generate the plurality of permutationsof the image file in batches. For example, a first virtual machine maygenerate a first permutation of the image file and a second virtualmachine may generate a second permutation of the image file (e.g., batch1), and then the first virtual machine may generate a third permutationof the image file and the second virtual machine may generate a fourthpermutation of the image file (e.g., batch 2), and so on. In this way,the imaging platform uses the plurality of virtual machines in aparallelized way to generate the plurality of permutations of the imagefile. This reduces an amount of time it takes the imaging platform togenerate the plurality of permutations, which in turn reduces an amountof time it takes the imaging platform to generate the aggregated imagefile.

A virtual machine may generate a permutation of the image file based onan organizational role received at the virtual machine. To generate thepermutation of the image file, the virtual machine may modify the copyof the image file based on a role configuration, stored in the role datastore, associated with the received organizational role. For example, ifthe virtual machine receives a graphic designer organizational role, thevirtual machine may add a device driver for a graphics tablet to thecopy of the image file, may add one or more graphic design softwareapplications to the copy of the image file, and/or the like.

Turning now to FIG. 1D, and as shown by reference number 110, theimaging platform may generate the aggregated image file. The aggregatedimage file may include the plurality of permutations of the image filegenerated by the plurality of virtual machines. The imaging platform maygenerate the aggregated image file by combining the plurality of thepermutations of the image file.

In some implementations, when combining the plurality of permutations ofthe image file, the imaging platform may deduplicate the plurality ofpermutations of the image file to reduce a size of the aggregated imagefile. The imaging platform may deduplicate the plurality of permutationsof the image file by including, in the aggregated image file, only onecopy of a software element if the software element is included in morethan one permutation, of the plurality of permutations, of the imagefile. For example, if a first permutation of the image file and a secondpermutation of the image file each include a same word processingsoftware application, the imaging platform may incorporate one copy ofthe word processing software application in the aggregated image file.In some implementations, the imaging platform may perform deduplicationof the plurality of permutations of the image file per software element(e.g., by comparing software elements included in each permutation, ofthe plurality of permutations, of the image file to determine redundantsoftware elements), per electronic file (e.g., by comparing electronicfiles included in each permutation, of the plurality of permutations, ofthe image file to determine redundant electronic files), and/or thelike.

In some implementations, the imaging platform may generate a respectiveinstruction (e.g., a script and/or the like) for a permutation of theimage file, included in the aggregated image file, and may include therespective instruction in the aggregated image file. The respectiveinstruction for the permutation of the image file may include aninstruction to install one or more software elements, associated withthe permutation of the image file and included in the aggregated imagefile (e.g., on a client device, on a server, and/or another device). Forexample, a respective instruction for a permutation of the image fileassociated with a publisher role may include an instruction to installan OS included in the aggregated image file, a publishing softwareapplication included in the aggregated image file, and/or the like, on aclient device.

Turning now to FIG. 1E, and as shown by reference number 112, theimaging platform may store the aggregated image file in an image filestore (e.g., a data structure on the image platform and/or anotherlocation in the network) along with other image files and/or otheraggregated image files. In some implementations, the imaging platformmay transmit the aggregated image file to the PXE server, to the one ormore client devices, and/or the like. In some implementations, insteadof, or in addition to, combining the plurality of permutations of theimage file into the aggregated image file, the imaging platform maystore the plurality of permutations of the image file in the image filestore.

For example, the imaging platform may provide a notification to a clientdevice that the aggregated image file is available in the image filestore. The imaging platform may receive, from the client device andbased on the notification, a request for the aggregated image file, andmay transmit the aggregated image file to the client device based onreceiving the request. The notification may be an email, a popupnotification on a graphical user interface (GUI) of the client device,and/or the like. In some implementations, the imaging platform mayprovide the notification at a periodic interval (e.g., once a day, oncean hour, etc.), and may adjust the periodic interval (e.g., provide thenotification once a day for one week, and then once an hour after theone week). In some implementations, a user of the client device mayinteract with the notification to transmit, to the imaging platform, therequest for the aggregated image file, to delay transmission of theaggregated image file to the client device, and/or the like.

In some implementations, when transmitting the aggregated image file toa client device, the imaging platform may identify an organizationalrole, of the plurality of organizational roles, assigned to the clientdevice (e.g., based on information stored on the client device, based onan asset tag assigned to the client device, based on a user associatedwith the client device, and/or the like), and may transmit, to theclient device, an instruction to install a permutation of the imagefile, included in the aggregated image file, associated with theorganizational role. The client device may receive the aggregated imagefile and the instruction, and may install the permutation of the imagefile, included in the aggregated image file, associated with theorganizational role, based on the received instruction. For example, thereceived instruction may include an instruction to execute a script,included in the aggregated image file, associated with the permutationof the image file. The client device may execute the script based on thereceived instruction, which may cause the client device to install, onthe client device, one or more software elements, associated with thepermutation of the image file, included in the aggregated image file.

In some implementations, the imaging platform may manage differentversions of an image file, an aggregated image file, and/or the like.For example, the imaging platform may store version 1.0 of an image filein the image file store, and may receive version 1.2 of the image file.Instead of transmitting the entire version 1.2 of the image file to theone or more client devices and/or the PXE server in the network, theimaging platform may generate a mapping table between the differentversions of the image file so that only portions that are differentbetween the different versions of the image file are transmitted to theone or more client devices and/or the PXE server in the network. In thisway, the imaging platform reduces the amount of network resources usedto transmit the updated version of the image file over the network andreduces the amount of storage resources used on the one or more clientdevices and/or the PXE server for storing image files.

Turning now to FIG. 1F, and as shown by reference number 114, theimaging platform may obtain a first version (e.g., a previous version,and old version, and outdated version, etc.) (e.g., version 1.0) of theimage file. For example, the imaging platform may obtain the firstversion of the image file from the image file store. As shown byreference number 116, the imaging platform may obtain a second version(e.g., a current version, a latest version, etc.) (e.g., version 1.2) ofthe image file. For example, the imaging platform may obtain the secondversion of the image file from the image file store.

As shown by reference number 118, the imaging platform may generate amapping table for the first version of the image file. The mapping tablemay include information identifying one or more portions of the firstversion of the image file that are not included in the second version ofthe image file (i.e., one or more portions that are new to the firstversion of the image file), information identifying one or more portionsof the second version of the image file that are not included in thefirst version of the image file (i.e., one or more portions that wereremoved from the second version of the image file), informationidentifying a mapping between one or more first portions of the firstversion of the image file that are unchanged from one or more secondportions of the second version of the image file, and/or the like. Anexample of a mapping table is described below in connection with FIG. 2.

A portion included in the first image file and/or a portion included inthe second version of the image file may be a software element, anelectronic file included in a software element, a segment of data of aspecific quantity (e.g., a 512 kilobyte segment of data, a 1 megabytesegment of data, etc.), and/or the like. For example, a portion includedin the first version of the image file may be associated with a graphicsediting software application, and a portion included in the secondversion of the image file may also be associated with the graphicsediting software application, may be associated with a differentsoftware application, or may be associated with a different softwareelement, such as a device driver, OS, and/or the like.

The imaging platform may determine that a first portion included in thefirst version of the software image is unchanged from a second portionincluded in the second version of the image file based on variousfactors, such as a version number of a software application associatedwith the first and second portions, based on detecting a change to oneor more electronic files included in the first and second portions,based on determining that a sequence of bits or bytes included in thefirst portion does not match a sequence of bits or bytes included in thesecond portion, and/or the like.

In some implementations, the imaging platform may generate the mappingtable for the first version of the image file by comparing the firstversion of the image file with the second version of the image file. Forexample, the imaging platform may compare a plurality of portions of thefirst version of the image file to a plurality of portions of the secondversion of the image file.

In some implementations, the imaging platform may perform a one-to-onecomparison of the plurality of portions of the first version of theimage and the plurality of portions of the second version of the imagefile. For example, the imaging platform may compare a first portion ofthe first version of the image file (e.g., a first 1 megabyte of thefirst version of the image file) with a second portion of the secondversion of the image file (e.g., a first 1 megabyte of the secondversion of the image file), may compare a third portion of the firstversion of the image file (e.g., a second 1 megabyte of the firstversion of the image file) with a fourth portion of the second versionof the image file (e.g., a second 1 megabyte of the second version ofthe image file), and so on. The mapping table for the first version ofthe image file may include information identifying whether the firstportion of the first version of the image file and the second portion ofthe second version of the image file match (i.e., the first portion isthe same as the second portion, thus indicating that the first portionis unchanged from the second portion), whether the third portion of thefirst version of the image file and the fourth portion of the secondversion of the image file match, and so on.

In some implementations, the imaging platform may compare each portion,of the plurality of portions, of the first version of the image file tothe plurality of portions of the second version of the image file. Forexample, the imaging platform may compare a first megabyte of the firstversion of the image file to all of the megabytes (or the megabytes thathave not already been identified as being mapped to another megabyte inthe first version of the image file) of the second version of the imagefile, may compare a second megabyte of the first version of the imagefile to all of the megabytes of the second version of the image file,and so on. The mapping table for the first version of the image file mayinclude information identifying a pointer to where each megabyte, in thefirst version of the image file, maps to the second version of the imagefile, if the imaging platform identifies a match for the megabyte.

As shown by reference number 120, the imaging platform may store themapping table for the first version of the image file, along with othermapping tables, in a mapping table store (e.g., a data structure on theimage platform and/or another location in the network).

In some implementations, a client device storing a second version of theimage file may request, from the imaging platform, the first version ofthe image file. The imaging platform may determine, based on receivingthe request for the first version of the image file, that the clientdevice is storing the second version of the image file. The imagingplatform may transmit, based on determining that the client device isstoring the second version of the image file, the mapping table for thefirst version of the image file to the client device. In this way, theclient device may download (e.g., from the imaging platform, from thePXE server, from another client device in the network, and/or the like)portions of the first version of the image file that are different fromthe second version of the image file instead of the entire first versionof this image file. This reduces the amount of storage resources on theclient device used for storing images files, and reduces the amount ofnetwork resources used to transmit image files over the network.

Turning now to FIG. 1G, and as shown by reference number 122, theimaging platform may periodically determine whether a client device, ofthe one or more client devices, is storing a current version of an imagefile. For example, the imaging platform may periodically (e.g., once aday, once a week, once a month, etc.) request version informationassociated with one or more image files stored on the client device. Theclient device may transmit, based on receiving the request, the versioninformation to the imaging platform. The version information mayidentify a respective version associated with an image file, of the oneor more image files, stored on the client device.

The imaging platform may determine that an image file, of the one ormore image files, stored on the client device is not the current versionof the image file based on receiving the version information from theclient device. To do so, the imaging platform may identify, based on theversion information, a respective version associated with the imagefile, and may compare the respective version associated with the imagefile with a version associated with a current version of the image filestored in the image file store. For example, the imaging platform maydetermine that the image file stored on the client device is version 1.0of the image file and may determine that the updated version of theimage file stored in the image file store is version 1.2 of the imagefile. Accordingly, the imaging platform may determine that the imagefile stored on the client device is a not the current version of theimage file based on the version 1.0 being older or prior to version 1.2.

Turning now to FIG. 1H, and as shown by reference number 124, theimaging platform may identify the current version of the image file,stored in the image file store, based on determining that the clientdevice is not storing the current version of the image file. As shown byreference number 126, the imaging platform may determine, based onidentifying the current version of the image file, a bandwidthallocation for transmitting the updated version of the image file to theclient device. The bandwidth allocation may specify an amount ofavailable bandwidth associated with a network connection of the clientdevice that may be used by the imaging platform to transmit the currentversion of the image file to the client device. For example, thebandwidth allocation may specify that the imaging platform may transmitthe current version of the image file to the client device using aportion (e.g., 30%, 50%, 70%, and/or the like) of the availablebandwidth associated with the network connection of the client device.

In some implementations, the bandwidth allocation may vary based on atime of day. For example, the bandwidth allocation may specify that theimaging platform may transmit the current version of the image file tothe client device using 30% of the available bandwidth associated withthe network connection of the client device during the hours of 9:00 amand 7:00 pm. It may further determine that it may use 80% of theavailable bandwidth associated with the network connection of the clientdevice during the hours of 7:00 pm and 8:00 am. In this way, the imagingplatform may transmit the current version of the image file to theclient device in a way that does not utilize the entire availablebandwidth associated with a network connection of the client device whenthe client device is likely to be active, which allows the client deviceto utilize the network connection for other functions while receivingthe current version of the image file. Moreover, this allows the imagingplatform to utilize a greater percentage of the available bandwidthassociated with the network connection of the client device when theclient device is likely to be idle.

The available bandwidth of the network connection associated with theclient device may be defined as an amount of data that can betransferred to the client device (i.e., downloaded) in a given period oftime. For example, the available bandwidth of the network connectionassociated with the client device may be defined in megabits per second(Mbps) megabytes per second (Mb/s), gigabits per second (Gbps),gigabytes per second (Gb/s), and/or the like. The imaging platform maydetermine the available bandwidth of the network connection associatedwith the client device based on various factors and/or using varioustechniques. For example, the imaging platform may transmit a test fileto the client device and may determine the available bandwidth based ontransmitting the test file to the client device (e.g., based on a rateof transfer of the test file to the client device). As an example, theimaging platform may transmit the test file to the client device and maydetermine the rate of transfer of the test file to the client device tobe 100 Mbps, and may therefore determine that the available bandwidth is100 Mbps. In some implementations, the imaging platform may transmit aplurality of test files to the client device, and may determine theavailable bandwidth by averaging the rate of transfers of the pluralityof test files.

In some implementations, the imaging platform may determine thebandwidth allocation for transmitting the current version of the imagefile to the client device based on one or more properties associatedwith a network connection of the client device, based on one or moreproperties associated with the client device, based on one or moreproperties associated with a site at which the client device is located,and/or the like. The one or more properties associated with the networkconnection of the client device may include a network connection type(e.g., Wi-Fi, wired Ethernet, virtual private network (VPN), and/or thelike) associated with the network connection of the client device, aquantity of other client devices in the same subnet as the clientdevice, a quantity of other devices located at the same site as theclient device, and/or the like. As an example, the imaging platform maydetermine the bandwidth allocation to be 50% of the available bandwidthassociated with the network connection of the client device based ondetermining that the network connection type of the network connectionof the client device is a Wi-Fi connection.

The one or more properties associated with the client device may includean organizational role assigned to the client device or a usage patternassociated with the client device (e.g., information identifying one ormore times a day the client device is active and/or idle). For example,the imaging platform may determine that the client device is assigned amedia streaming role (e.g., a client device that displays content in aretail store by streaming promotional videos from the Internet), and maytherefore determine the bandwidth allocation to be 20% of the availablebandwidth associated with the network connection of the client deviceduring store hours and 80% of the of the available bandwidth associatedwith the network connection of the client device outside of store hours.

The one or more properties associated with the site may include a sitetype (e.g., a retail store, an office, a training center, etc.), a typeof Internet service associated with the site (e.g., a T1 Internetservice, a wireless Internet service, a broadband Internet service, asatellite Internet service, etc.), hours of operation associated withthe site, and/or the like. For example, the imaging platform maydetermine that the client device is located at an office site that has aT1 Internet connection, and may therefore determine the bandwidthallocation to be 50% of the available bandwidth associated with thenetwork connection of the client device during office hours and 90% ofthe of the available bandwidth associated with the network connection ofthe client device outside of office hours.

In some implementations, the imaging platform may transmit aninstruction associated with the current version of the image file to theclient device, and may determine the bandwidth allocation fortransmitting the current version of the image file to the client devicebased on an instruction type associated with the instruction. Forexample, the instruction may be an instruction to repair the clientdevice (e.g., because the client device is unable to boot an OSinstalled on the client device), and the imaging platform may determinethe bandwidth allocation to be 95% of the available bandwidth associatedwith the network connection of the client device based on theinstruction being a repair instruction. In this way, since the clientdevice is not bootable and unable to use the network connectionassociated with the client device, the imaging platform may utilize mostof the available bandwidth associated with the network connection of theclient device to quickly repair the client device.

In some implementations, the imaging platform may dynamically adjust thebandwidth allocation for transmitting the current version of the imagefile to the client device. For example, the imaging platform maydetermine that the imaging platform is transmitting the current versionof the image file to the client device at a transfer rate that is lessthan the bandwidth allocation for transmitting the current version ofthe image file. This may occur when, for example, a user of the clientdevice is actively using the network connection associated with theclient device. The imaging platform may reduce the bandwidth allocationfor transmitting the current version of the image file to the clientdevice based on determining that the imaging platform is transmittingthe current version of the image file to the client device at thetransfer rate that is less than the bandwidth allocation fortransmitting the current version of the image file. In this way, theimaging platform may dynamically adjust the bandwidth allocation basedon client device activity to ensure that transmitting the currentversion of the image file to the client device does not adversely affectthe client device's use of the network connection associated with theclient device.

Turning now to FIG. 1I, and as shown by reference number 128, theimaging platform may transmit a mapping table associated with thecurrent version of the image file to the client device. The mappingtable for the current version of the image file may be generated asdescribed above. As shown by reference number 130, the imaging platformmay transmit, based on the determined bandwidth allocation, the currentversion of the image file to the client device.

In some implementations, the imaging platform may transmit, based on themapping table, a portion of the current version of the image file to theclient device. For example, the imaging platform may transmit theportion of the current version of the image file based on determiningthat the portion is different from a corresponding portion of the imagefile stored on the client device. The client device may receive themapping table and the portion of the current version of the image file,and may generate a copy of the current version of the image file bycombining, based on the mapping table, the portion of the currentversion of the image file with one or more unchanged portions of theimage file stored on the client device. In this way, the imagingplatform reduces network resource usage by transmitting less than theentire current version of the image file to the client device.

In some implementations, if the transfer of the current version of theimage file to the client device fails to complete (e.g., because thenetwork connection of the client device was terminated, because theclient device lost the connection to the imaging platform, etc.), theimaging platform and the client device may resume the transfer insteadof retransferring the entire current version of the image file. Forexample, the client device may determine that a file size of the currentversion of the image file received at the client device is less than anexpected file size. In this case, the client device may transmit, basedon determining that the size of the current version of the image filereceived at the client device is less than the expected file size, arequest to the imaging platform to resume transferring the currentversion of the image file. The imaging platform, based on receiving therequest, may determine an amount of data, associated with the currentversion of the image file, that has been already transferred to theclient device (e.g., based on the file size of the current version ofthe image file on the client device), and may resume the transfer of thecurrent version of the image file based on the amount of data that hasalready been transferred to the client device. For example, the imagingplatform may determine that file size of the current version of theimage file on the client device is 10,130 megabytes and the expectedfile size for the current version of the image file is 10,230 megabytes,and may therefore resume the transfer of the current version of theimage file at megabyte 10,131. In this way, the imaging platform mayresume the transfer of the current version of the image file instead ofretransferring the entire current version of the image file, whichreduces the amount of data transmitted over the network.

Turning now to FIG. 1J, in some implementations, instead of transmittingan image file directly to a client device of the one or more clientdevices (e.g., client device 1, client device 2, and/or the like), theimaging platform may transmit the image file to the PXE server on thesame subnet as the client device, along with instructions for the PXEserver to transmit the image file to the client device. As shown byreference number 132, the imaging platform may transmit an image file(or aggregated image file) to the PXE server. In some implementations,the imaging platform may transmit the image file to the PXE server basedon a bandwidth allocation, as described above. In some implementations,the imaging platform may transmit a mapping table associated with theimage file, as described above. As shown by reference number 134, theimaging platform may transmit an instruction to the PXE server. Theinstruction may be an instruction to transmit the image file to a clientdevice (e.g., client device 1), to install a software element on theclient device from the image file, and/or the like. As shown byreference number 136, the PXE server may transmit, based on theinstruction, the image file to client device 1. In some implementations,client device 1 may store the image file on client device 1, install thesoftware element from the image file on client device 1, transmit theimage file to another client device (e.g., client device 2), and/or thelike. In this way, the imaging server may store the image file in acentralized location in the subnet so that the image file may be locallytransferred to the client devices in the subnet.

Turning now to FIG. 1K, the imaging platform may transmit variousinstructions to the one or more client devices in the subnet. As shownby reference number 138, the imaging platform may transmit aninstruction to client device 1. The instruction may be an instruction totransmit an image file, stored on client device 1, to client device 2.As shown by reference number 140, client device 1 may transmit the imagefile to client device 2 based on receiving the instruction from theimaging platform. In this way, the image file may be locally transferredfrom client device 1 to client device 2 using the subnet instead oftransferring the image file from the imaging platform to client device 2over the network, which reduces the amount of network resources used totransmit the image file to client device 2.

Turning now to FIG. 1L, the imaging platform may transmit an instructionto a client device in the subnet (e.g., client device 2), based onreceiving information from client device 2. In some implementations, theimaging platform may select a client device (e.g., client device 2), ofthe one or more client devices, the PXE server, or another device in thesubnet, as a master device for the subnet. The master device may managethe other client devices (e.g., client device 1 and/or the like) in thesubnet, and may transmit information associated with the other clientdevices in the subnet to the imaging platform. For example, clientdevice 2 may determine that client device 1 is in an idle state. Theidle state may be a state where client device 1 is in a sleep mode or astandby mode, where one or more devices of client device 1 are turnedoff, and an operating state of client device 1 is stored in a memorycomponent so that client device 1 may use the stored operating state toresume operations when client device 1 transitions into an active state.As shown by reference number 142, client device 2 may transmit, to theimaging platform, information identifying that client device 1 is in theidle state.

Turning now to FIG. 1M, the imaging platform may receive the informationidentifying that client device 1 is in the idle state, and may performan action based on receiving the information. For example, the imagingplatform may seek to transmit an image file to client device 1, butclient device 1 is in the idle state. Accordingly, as shown by referencenumber 144 the imaging platform may transmit an instruction to clientdevice 2. The instruction may be an instruction to transmit a wakeinstruction to client device 1. As shown by reference number 146, clientdevice 2 may transmit the wake instruction to client device 1 based onreceiving the instruction from the imaging platform. In someimplementations, the wake instruction may include information indicatingto client device 1 that the imaging platform is attempting to transferthe image file to client device 1.

As shown by reference number 148, client device 1 may transition fromthe idle state to the active state, which, as explained above, mayinclude loading the operating state stored in the memory component ofclient device 1 to resume operations of client device 1. As shown byreference number 150, client device 1 may transmit, based on receivingthe wake command and transitioning to the active state, a request forthe image file to the imaging platform.

Turning now to FIG. 1N, and as shown by reference number 152, theimaging platform may receive the request from client device 1, and maytransmit the image file to client device 1 based on receiving therequest.

In some implementations, the imaging platform may transmit otherinstructions to the one or more client devices in the subnet, to the PXEserver in the subnet, and/or another device in the subnet. For example,the imaging platform may transmit an instruction to client device 1 toinstall a software element (e.g., an OS, a software application, adevice driver, etc.) from the image file transmitted to client device 1.In some implementations, before installing an OS from the image file,the imaging platform may transmit an instruction to client device 1 forclient device 1 to transmit configuration information associated withclient device 1 (e.g., one or more settings of basic input/output system(BIOS) of client device 1, information included in a trusted platformmodule (TPM) component on client device 1, OS version information,static IP address information associated with client device 1 so thatthe imaging platform may restore the static IP address of client device1 after the OS is installed, and/or the like) to the imaging platform.In some implementations, before installing the OS from the image file,the imaging platform may transmit an instruction to client device 1 forclient device 1 to change a partition table of client device 1 (e.g.,from a master boot record (MBR) partition table to a globally uniqueidentifier (GUID) partition table (GPT), and/or the like). In someimplementations, the imaging platform may transmit a first instructionto client device 1 for client device 1 to transmit data stored on clientdevice 1 to another client device in the subnet (e.g., client device 2)before installing the OS from the image file. After client device 1installs the OS, the imaging platform may transmit a second instructionto client device 1 for client device 1 to obtain the data stored onclient device 2. In this way, the data is not overwritten or erased byinstallation of the OS on client device 1.

In some implementations, the imaging platform may transmit aninstruction to the master device and/or the PXE server based ondetecting an event in the subnet. For example, the imaging platform maybe transferring an image file to client device 1, and the master devicemay detect that transfer has stalled (e.g., client device 1 has receivedan amount of data associated with the image file in a particular timeperiod that does not satisfy a threshold amount of data). The masterdevice may transmit, based on determining that the transfer has stalled,a notification to the imaging platform that an event has occurred (i.e.,the transfer of the image file to client device 1 has stalled) in thesubnet. Based on the notification, the imaging platform may transmit aninstruction to the master device to provide a reboot instruction toclient device 1 to reboot client device 1. Client device 1 may rebootbased on receiving the reboot instruction, and may attempt to resume thetransfer after rebooting, as described above.

In some implementations, a client device (e.g., client device 1) maytransmit information to another client device in the subnet, to the PXEserver, and/or to the imaging platform without receiving instructionsfrom the other client device, the PXE server, or the imaging platform.For example, client device 1 may transmit configuration informationassociated with client device 1 (e.g., one or more settings of the BIOSof client device 1, information included in the TPM component on clientdevice 1, OS version information, static IP address informationassociated with client device 1), status updates (e.g., an updateindicating that an image file was downloaded by client device 1, astatus update indicating that a software application was installed onclient device 1, etc.), and/or the like to the imaging platform.

Turning now to FIG. 1O, a client device that receives an image file maydetermine whether the received image file is corrupted (e.g., fromtransmitting the image file to the client device, from storing the imagefile on the client device, etc.). The client device may determine if thereceived image file was corrupted using a hashing function, such as asecure hash algorithm (SHA), an MD5 hash algorithm, and/or the like. Insome implementations, the client device may store the received imagefile in a storage component (e.g., a solid-state drive, a hard diskdrive, and/or the like) on the client device, generate a hash value forthe received image file (e.g., using a hashing function listed above),may compare the generated hash value with an expected hash value for thereceived image file, and may determine that the received image file wascorrupted based on determining that the generated hash value does notmatch the expected hash value. However, the storage component may be arelatively slow storage medium, such as a flash-based storage medium ora magnetic disk-based storage medium, and computing the hash value forthe received image file (which may be on the order of tens of gigabytesin size), while the received image file is stored in the storagecomponent, may take a significant amount of time.

To reduce the amount of time it takes to compute the hash value for thereceived image file, the client device may compute a plurality ofintermediate hash values for the received image file, while the receivedimage file is in a memory component on the client device (which may be amedium, such as a dynamic random access memory (DRAM), a nonvolatilerandom access memory (NVRAM), and/or the like, that is relatively fasterthan the medium of the storage component), and may compute a final hashvalue for the received image file from the plurality of intermediatehash values.

As shown by reference number 154, the client device may provide arequest to the imaging platform for the image file. In someimplementations, the image file may be an aggregated image file, asdescribed above. As shown by reference number 156, the imaging platformmay receive the request, segment the image file into a plurality ofportions (e.g., 50 megabyte portions, 100 megabyte portions, etc.), andtransmit the plurality of portions of the image file to the clientdevice. In some implementations, the imaging platform may determineand/or adjust the size of the plurality of portions. For example, theimaging platform may determine a size of the memory component on theclient (e.g., by requesting information, from the client device,identifying the size of the memory component), and may determine thesize of the plurality of the portions based on the size of the memorycomponent on the client device.

As shown by reference number 158, the client device may receive aportion, of the plurality of portions, of the image file, and may storethe portion of the image file in the memory component on the clientdevice. As shown by reference number 160, while the portion of the imagefile is still in the memory component on the client device, the clientdevice may generate an intermediate hash value for the portion of theimage file. The intermediate hash value may be a hash value specific tothe portion of the image file. The client device may generate theintermediate hash value using one or more of the hashing functionsdescribed above.

As shown by reference number 162, the client device may transfer, basedon generating the intermediate hash value for the portion of the imagefile, the portion of the image file to the storage component on theclient device. In some implementations, the client device may store theportion of the image file as an electronic file in the storagecomponent. The client device may repeat the actions described inconnection with reference numbers 158-162 for the remaining portions, inthe plurality of portions, of the image file.

Turning now to FIG. 1P, and as shown by reference number 164, the clientdevice may combine the plurality of portions of the image file, in thestorage component on the client device, to generate a copy of the imagefile. For example, the client device may combine the plurality ofportions of the image file by combining the plurality of electronicfiles, associated with the plurality of portions of the image file, intoa single electronic file associated with the copy of the image file.

As shown by reference number 166, the client device may generate a finalhash value for the copy of the image file. The client device maygenerate the final hash value based on the plurality of intermediatehash values. For example, the client device may generate the final hashvalue by concatenating the intermediate hash values, by using theintermediate hash values in a hashing function described above, and/orthe like.

As shown by reference number 168, the client device may compare thefinal hash value for the copy of the image file with an expected hashvalue for the copy of the image file. The client device may determinewhether the final hash value and the expected hash value match. Forexample, the final hash value and the expected hash value may each be astring of alphanumeric characters, and the client device may compare thestring of alphanumeric characters for the final hash value with thestring of alphanumeric characters for the expected hash value. If thestring of alphanumeric characters for the final hash value and thestring of alphanumeric characters for the expected hash value are thesame, the client device may determine that the final hash value and theexpected hash value match.

As shown by reference number 170, the client device may store, on theclient device, the copy of the image file based on determining that thefinal hash value and the expected hash value match. The client devicemay store the copy of the image file in an image file store (e.g., afile folder, an archive, and/or the like) on the storage component ofthe client device. In some implementations, if the client devicedetermines that the final hash value and the expected hash value do notmatch, the client device may discard the copy of the image file (e.g.,by deleting the copy of the image file from the storage component) andtransmit a request to the imaging platform to retransmit the image fileto the client device.

The number and arrangement of devices and networks shown in FIGS. 1A-1Pare provided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIGS. 1A-1P. Furthermore, two or more devices shown in FIGS.1A-1P may be implemented within a single device, or a single deviceshown in FIGS. 1A-1P may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) shown in FIGS. 1A-1P may perform one or more functionsdescribed as being performed by another set of devices of FIGS. 1A-1P.

FIG. 2 is a diagram of an example mapping table 200. In someimplementations, an imaging platform may generate mapping table 200, andmay transmit mapping table 200 to a client device, as described above inconnection with FIGS. 1A-1P. In some implementations, the client devicemay receive mapping table 200, and may use mapping table 200 to request,from the imaging platform, one or more portions of a first version(e.g., a current version, an updated version, a new version, etc.) of animage file (e.g., image file v1.2) that are unchanged from a secondversion (e.g., a previous version, an older version, and outdatedversion, etc.) of the image file (e.g., image file v1.0) stored on theclient device.

As shown in FIG. 2, mapping table 200 may include informationidentifying a first plurality of portions included in image file v1.2(e.g., portion 1 through portion n, where n≥1), information identifyinga second plurality of portions included in image file v1.0 (e.g.,portion 1 through portion m, where m≥1). In some implementations, aquantity of the first plurality of portions may be the same as aquantity of the second plurality of portions. In some implementations,the quantity of the first plurality of portions may be different fromthe quantity of the second plurality of portions. As explained above inconnection with FIGS. 1A-1P, the plurality of portions included in imagefile v1.2 and/or image file v1.0 may include a software element, anelectronic file included in a software element, a segment of data of aspecific quantity (e.g., a 512 kilobyte segment of data, a 1 megabytesegment of data, etc.), and/or the like.

As further shown in FIG. 2, mapping table 200 may include informationidentifying whether portion 1 through portion n of image file v1.2 match(and are thus unchanged from) any of portion 1 through portion m ofimage file v1.0. For example, and as shown in FIG. 2, a first portion,of the first plurality of portions, included in image file v1.2 (e.g.,portion 1 of image file v1.2) and a second portion, of the secondplurality of portions, included in image file v1.0 (e.g., portion 1 ofimage file v1.0) match (thus indicating that the first portion isunchanged from the second portion), whether a third portion, of thefirst plurality of portions, included in image file v1.2 (e.g., portion2 of image file v1.2) and a fourth portion, of the second plurality ofportions, included in image file v1.0 (e.g., portion 3 of image filev1.0) match (thus indicating that the third portion is unchanged fromthe fourth portion), and so on. Portion 1 of image file v1.2 and Portion1 of image file v1.0 may be identified as a match if one or more bits inPortion 1 of image file v1.2 and one or more bits in Portion 1 of imagefile v1.0 match. For example, Portion 1 of image file v1.2 may be a 1megabyte segment of data included in image file v1.2, and Portion 1 ofimage file v1.0 may be a 1 megabyte segment of data included in imagefile v1.0. The 1 megabyte segment of data included in image file v1.2and the 1 megabyte segment of data included in image file v1.0 may beidentified as a match if the one or more bits in the 1 megabyte segmentof data included in image file v1.2 and the one or more bits in the 1megabyte segment of data included in image file v1.0 match.

If a portion of image file v1.2 has no corresponding portion in imagefile v1.0 (e.g., portion 3 of image file v1.2), mapping table 200 mayinclude information identifying that the portion of image file v1.2 isnew from image file v1.0. If a portion of image file v1.0 has nocorresponding portion in image file v1.2 (e.g., portion 2 of image filev1.0), mapping table may include information identifying that theportion of image file v1.0 is not included in image file v1.2.

FIG. 3 is a diagram of an example environment 300 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.3, environment 300 may include a client device 310, a server device 320,an imaging platform 330 in a cloud computing environment 332 thatincludes a set of computing resources 334, and a network 340. Devices ofenvironment 300 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

Client device 310 includes one or more devices capable of receiving,generating, storing, processing, and/or providing data associated withan image file. For example, client device 310 may transmit informationto imaging platform 330 (e.g., version information associated with animage file stored on client device 310, BIOS configuration informationfor client device 310, information included in a TPM component includedin client device 310, etc.). As another example, client device 310 mayrequest an image file (e.g., from another client device 310, serverdevice 320, imaging platform 330, etc.) and may receive the image file(e.g., from another client device 310, server device 320, imagingplatform 330, etc.). In some implementations, client device 310 mayreceive a plurality of portions of an image file, and may combine theplurality of portions of the image file. As another example, clientdevice 310 may receive an instruction (e.g., from another client device310, server device 320, imaging platform 330, etc.), and may perform anaction associated with the instruction (e.g., install a software elementfrom an image file, transmit an instruction to another client device310, transmit an image file to another client device 310, etc.). In someimplementations, client device 310 may include a device equipped with acommunication interface, such as a mobile phone (e.g., a smart phone, aradiotelephone, etc.), a desktop computer, a laptop computer, a tabletcomputer, a handheld computer, or a similar type of device.

Server device 320 includes one or more devices capable of receiving,generating storing, processing, and/or providing data associated with animage file. For example, server device 320 may receive an image filefrom imaging platform 330, and may transmit the image file to clientdevice 310. As another example, server device 320 may receive aninstruction from imaging platform 330, and may transmit anotherinstruction (e.g., an instruction to install a software element from theimage file) based on receiving the instruction. As another example,server device 320 may transmit an image file to client device 310 basedon receiving a request, from client device 310, for the image file. Insome implementations, server device 320 may be a preboot executionenvironment (PXE) server. In some implementations, server device 320 mayinclude a server (e.g., in a data center or a cloud computingenvironment), a data center (e.g., a multi-server micro datacenter), aworkstation computer, a virtual machine (VM) provided in a cloudcomputing environment, or a similar type of device. In someimplementations, server device 320 may include a communication interfacethat allows server device 320 to receive information from and/ortransmit information to other devices in environment 300. In someimplementations, server device 320 may be a physical device implementedwithin a housing, such as a chassis. In some implementations, serverdevice 320 may be a virtual device implemented by one or more computerdevices of a cloud computing environment or a data center.

Imaging platform 330 includes one or more devices capable of generatingand managing image files. For example, imaging platform 330 may receivean image file, generate an aggregated image from the image file (e.g.,including a plurality of permutations of the image file), transmit theaggregated image file (or another image file) to client device 310,server device 320, and/or the like. As another example, imaging platform330 may transmit an instruction to client device 310, server device 320,and/or the like, such as an instruction to install a software elementfrom an image file, an instruction to transmit another instruction toclient device 310, server device 320, and/or the like, an instruction toprovide information to imaging platform 330, and/or the like. In someimplementations, as shown, imaging platform 330 may be hosted in cloudcomputing environment 332. Notably, while implementations describedherein describe imaging platform 330 as being hosted in cloud computingenvironment 332, in some implementations, imaging platform 330 may notbe cloud-based (i.e., may be implemented outside of a cloud computingenvironment) or may be partially cloud-based.

Cloud computing environment 332 includes an environment that hostsimaging platform 330. Cloud computing environment 332 may providecomputation, software, data access, storage, and/or other services. Asshown, cloud computing environment 332 may include a group of computingresources 334 (referred to collectively as “computing resources 334” andindividually as “computing resource 334”).

Computing resource 334 includes one or more personal computers,workstation computers, server devices, or another type of computationand/or communication device. In some implementations, computing resource334 may host imaging platform 330. The cloud resources may includecompute instances executing in computing resource 334, storage devicesprovided in computing resource 334, data transfer devices provided bycomputing resource 334, etc. In some implementations, computing resource334 may communicate with other computing resources 334 via wiredconnections, wireless connections, or a combination of wired andwireless connections.

As further shown in FIG. 3, computing resource 334 may include a groupof cloud resources, such as one or more applications (“APPs”) 334-1, oneor more virtual machines (“VMs”) 334-2, one or more virtualized storages(“VSs”) 334-3, or one or more hypervisors (“HYPs”) 334-4.

Application 334-1 includes one or more software applications that may beprovided to or accessed by one or more devices of environment 300.Application 334-1 may eliminate a need to install and execute thesoftware applications on devices of environment 300. For example,application 334-1 may include software associated with imaging platform330 and/or any other software capable of being provided via cloudcomputing environment 332. In some implementations, one application334-1 may send/receive information to/from one or more otherapplications 334-1, via virtual machine 334-2. In some implementations,application 334-1 may include a software application associated with oneor more databases and/or operating systems. For example, application334-1 may include an enterprise application, a functional application,an analytics application, and/or the like.

Virtual machine 334-2 includes a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 334-2 may be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 334-2. A system virtual machinemay provide a complete system platform that supports execution of acomplete operating system (“OS”). A process virtual machine may executea single program, and may support a single process. In someimplementations, virtual machine 334-2 may execute on behalf of a user(e.g., a user of client device 310), and may manage infrastructure ofcloud computing environment 332, such as data management,synchronization, or long-duration data transfers.

Virtualized storage 334-3 includes one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 334. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 334-4 provides hardware virtualization techniques that allowmultiple operating systems (e.g., “guest operating systems”) to executeconcurrently on a host computer, such as computing resource 334.Hypervisor 334-4 may present a virtual operating platform to the guestoperating systems, and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

Network 340 includes one or more wired and/or wireless networks. Forexample, network 340 may include a mobile network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, etc.), a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, or thelike, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 3 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 3. Furthermore, two or more devices shown in FIG. 3 may beimplemented within a single device, or a single device shown in FIG. 3may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 300 may perform one or more functions described as beingperformed by another set of devices of environment 300.

FIG. 4 is a diagram of example components of a device 400. Device 400may correspond to client device 310, server device 320, imaging platform330, and/or various devices included in network 340. In someimplementations client device 310, server device 320, imaging platform330, and/or various devices included in network 340 may include one ormore devices 400 and/or one or more components of device 400. As shownin FIG. 4, device 400 may include a bus 410, a processor 420, a memory430, a storage component 440, an input component 450, an outputcomponent 460, and a communication interface 470.

Bus 410 includes a component that permits communication among thecomponents of device 400. Processor 420 is implemented in hardware,firmware, or a combination of hardware and software. Processor 420 takesthe form of a central processing unit (CPU), a graphics processing unit(GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), or another type ofprocessing component. In some implementations, processor 420 includesone or more processors capable of being programmed to perform afunction. Memory 430 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 420.

Storage component 440 stores information and/or software related to theoperation and use of device 400. For example, storage component 440 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 450 includes a component that permits device 400 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 450 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 460 includes a component that providesoutput information from device 400 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 470 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 400 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 470 may permit device 400to receive information from another device and/or provide information toanother device. For example, communication interface 470 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a wireless local area network interface, a cellularnetwork interface, or the like.

Device 400 may perform one or more processes described herein. Device400 may perform these processes based on processor 420 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 430 and/or storage component 440. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 430 and/or storagecomponent 440 from another computer-readable medium or from anotherdevice via communication interface 470. When executed, softwareinstructions stored in memory 430 and/or storage component 440 may causeprocessor 420 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 4 are provided asan example. In practice, device 400 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 4. Additionally, or alternatively, aset of components (e.g., one or more components) of device 400 mayperform one or more functions described as being performed by anotherset of components of device 400.

FIG. 5 is a flow chart of an example process 500 for image filegeneration and management. In some implementations, one or more processblocks of FIG. 5 may be performed by an imaging platform (e.g., imagingplatform 330). In some implementations, one or more process blocks ofFIG. 5 may be performed by another device or a group of devices separatefrom or including the imaging platform, such as a client device (e.g.,client device 310), and/or a server device (e.g., server device 320).

As shown in FIG. 5, process 500 may include periodically determiningwhether an image file stored on a client device is a current version ofthe image file (block 510). For example, the imaging platform (e.g.,using processor 420, memory 430, input component 450, communicationinterface 470, and/or the like) may periodically determine whether animage file stored on a client device is a current version of the imagefile, as described above in connection with FIGS. 1A-1P.

As further shown in FIG. 5, process 500 may include identifying, basedon determining that the image file on the client device is not thecurrent version of the image file, the current version of the image filein an image file store (block 520). For example, the imaging platform(e.g., using processor 420, memory 430, input component 450,communication interface 470, and/or the like) may identify, based ondetermining that the image file on the client device is not the currentversion of the image file, the current version of the image file in animage file store, as described above in connection with FIGS. 1A-1P.

As further shown in FIG. 5, process 500 may include determining, basedon identifying the current version of the image file and based on one ormore properties associated with a network connection of the clientdevice, a bandwidth allocation (block 530). For example, the imagingplatform (e.g., using processor 420, memory 430, input component 450,communication interface 470, and/or the like) may determine, based onidentifying the current version of the image file and based on one ormore properties associated with a network connection of the clientdevice, a bandwidth allocation, as described above in connection withFIGS. 1A-1P. In some implementations, the one or more propertiesassociated with the network connection of the client device may includeat least a network connection type of a plurality of network connectiontypes. In some implementations, the bandwidth allocation may specify anamount of bandwidth, of an available bandwidth for the networkconnection of the client device, that is to be used for transmitting thecurrent version of the image file to the client device. In someimplementations, the amount of bandwidth that is to be used fortransmitting the current version of the image file to the client devicemay be less than the available bandwidth for the network connection ofthe client device.

As further shown in FIG. 5, process 500 may include transmitting, to theclient device, a mapping table associated with the current version ofthe image file (block 540). For example, the imaging platform may (e.g.,using processor 420, memory 430, input component 450, output component460, communication interface 470, and/or the like) transmit, to theclient device, a mapping table associated with the current version ofthe image file, as described above in connection with FIGS. 1A-1P.

As further shown in FIG. 5, process 500 may include transmitting, basedon the bandwidth allocation and based on the mapping table, the currentversion of the image file to the client device (block 550). For example,the imaging platform (e.g., using processor 420, memory 430, inputcomponent 450, output component 460, communication interface 470, and/orthe like) may transmit, based on the bandwidth allocation and based onthe mapping table, the current version of the image file to the clientdevice, as described above in connection with FIGS. 1A-1P.

Process 500 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or described with regard to any other process described herein.

In some implementations, when determining the bandwidth allocation fortransmitting the image file to the client device, the imaging platformmay transmit a test file to the client device, may determine, based ontransmitting the test file to the client device, the available bandwidthfor the network connection of the client device.

In some implementations, the network connection type may include a wiredEthernet connection, a wireless connection, and/or a VPN connection. Insome implementations, each of the plurality of network connection typesmay be associated with a different bandwidth allocation for transmittingthe current version of the image file to the client device.

In some implementations, when determining the bandwidth allocation fortransmitting the current version of the image file to the client device,the imaging platform may determine the bandwidth allocation fortransmitting the current version of the image file to the client devicefurther based on a time of day that the current version of the imagefile is to be transmitted to the client device or a type of work orderassociated with the current version of the image file.

In some implementations, the imaging platform may determine that thecurrent version of the image file is being transmitted to the clientdevice at a transfer rate that is less than the bandwidth allocation fortransmitting the current version of the image file to the client device,and may reduce the bandwidth allocation for transmitting the currentversion of the image file to the client device based on determining thatthe current version of the image file is being transmitted to the clientdevice at the transfer rate that is less than the bandwidth allocationfor transmitting the current version of the image file to the clientdevice.

In some implementations, the mapping table, associated with the currentversion of the image file, may include information identifying a mappingbetween one or more first portions of the current version of the imagefile and one or more second portions of the image file stored on theclient device. In some implementations, the one or more first portionsof the current version of the image file may be unchanged from the oneor more second portions of the image file stored on the client device.

In some implementations, when transmitting the current version of theimage file to the client device, the imaging platform may transmit oneor more portions of the current version of the image file to the clientdevice. In some implementations, the one or more portions of the currentversion of the image file may not be included in the image file storedon the client device.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 for image filegeneration and management. In some implementations, one or more processblocks of FIG. 6 may be performed by an imaging platform (e.g., imagingplatform 330). In some implementations, one or more process blocks ofFIG. 6 may be performed by another device or a group of devices separatefrom or including the imaging platform, such as a client device (e.g.,client device 310), and/or a server device (e.g., server device 320).

As shown in FIG. 6, process 600 may include receiving an image file(block 610). For example, the imaging platform (e.g., using processor420, memory 430, storage component 440, input component 450,communication interface 470, and/or the like) may receive an image file,as described above in connection with FIGS. 1A-1P.

As further shown in FIG. 6, process 600 may include identifying, basedon receiving the image file, a plurality of organizational roles (block620). For example, the imaging platform (e.g., using processor 420,memory 430, input component 450, communication interface 470, and/or thelike) may identify, based on receiving the image file, a plurality oforganizational roles, as described above in connection with FIGS. 1A-1P.

As further shown in FIG. 6, process 600 may include distributing a copyof the image file and an organizational role, of the plurality oforganizational roles, to each VM of a plurality of VMs (block 630). Forexample, the imaging platform (e.g., using processor 420, memory 430,input component 450, output component 460, communication interface 470,and/or the like) may distribute a copy of the image file and anorganizational role, of the plurality of organizational roles, to eachVM of a plurality of VMs, as described above in connection with FIGS.1A-1P.

As further shown in FIG. 6, process 600 may include generating, by a VMof the plurality of VMs, a permutation of the image file, based on theorganizational role distributed to the VM, from a copy of the image filedistributed to the VM (block 640). For example, the imaging platform may(e.g., using processor 420, memory 430, and/or the like) generate, by aVM of the plurality of VMs, a permutation of the image file, based onthe organizational role distributed to the VM, from a copy of the imagefile distributed to the VM, as described above in connection with FIGS.1A-1P.

As further shown in FIG. 6, process 600 may include generating anaggregated image file that includes each permutation of the image fileassociated with each organizational role of the plurality oforganizational roles (block 650). For example, the imaging platform(e.g., using processor 420, memory 430, and/or the like) may generate,by the imaging device, an aggregated image file that includes eachpermutation of the image file associated with each organizational roleof the plurality of organizational roles, as described above inconnection with FIGS. 1A-1P.

As further shown in FIG. 6, process 600 may include transmitting theaggregated image file to a client device (block 660). For example, theimaging platform may (e.g., using processor 420, memory 430, outputcomponent 460, communication interface 470, and/or the like) transmit,by the imaging device, the aggregated image file to a client device, asdescribed above in connection with FIGS. 1A-1P.

Process 600 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, the imaging platform may identify anorganizational role, of the plurality of organizational roles, assignedto the client device, and may transmit, to the client device, aninstruction to install a permutation of the image file, included in theaggregated image file, associated with the organizational role assignedto the client device.

In some implementations, when transmitting the aggregated image file tothe client device, the imaging platform may transmit the aggregatedimage file to a plurality of client devices on a same subnet. In someimplementations, when transmitting the aggregated image file to theclient device, the imaging platform may transmit the aggregated imagefile to a PXE server on a same subnet as the client device, and maytransmit an instruction to the PXE server to provide the aggregatedimage file to the client device.

In some implementations, when transmitting the aggregated image file tothe client device, the imaging platform may provide, to the clientdevice, a notification that the aggregated image file is available in animage store, may receive, from the client device and based on thenotification, a request for the aggregated image file, and may transmitthe aggregated image file to the client device based on receiving therequest.

In some implementations, the imaging platform may generate a mappingtable for the aggregated image file, and may transmit the aggregatedimage file to the client device based on the mapping table. In someimplementations, the mapping table for the aggregated image file mayinclude information identifying a mapping between one or more firstportions of the aggregated image file and one or more second portions ofanother version of the aggregated image file. In some implementations,the one or more first portions of the aggregated image file may beunchanged from the one or more second portions of the other version ofthe aggregated image file.

In some implementations, the imaging platform may, prior to transmittingthe aggregated image file to the client device, detect that the clientdevice is in an idle state, and may transmit, to a master device on asame subnet as the client device, an instruction to provide the clientdevice with a wake instruction based on detecting that the client deviceis in the idle state.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

FIG. 7 is a flow chart of an example process 700 for image filegeneration and management. In some implementations, one or more processblocks of FIG. 7 may be performed by a client device (e.g., clientdevice 310). In some implementations, one or more process blocks of FIG.7 may be performed by another device or a group of devices separate fromor including the imaging platform, such as a plurality of client devices310, a server device (e.g., server device 320) and/or an imagingplatform (e.g., imaging platform 330).

As shown in FIG. 7, process 700 may include transmitting a request foran image file (block 710). For example, the client device (e.g., usingprocessor 420, memory 430, output component 460, communication interface470, and/or the like) may transmit a request for an image file, asdescribed above in connection with FIGS. 1A-1P.

As further shown in FIG. 7, process 700 may include receiving, based ontransmitting the request, a plurality of portions of the image file(block 720). For example, the client device (e.g., using processor 420,memory 430, input component 450, communication interface 470, and/or thelike) may receive, based on transmitting the request, a plurality ofportions of the image file, as described above in connection with FIGS.1A-1P.

As further shown in FIG. 7, process 700 may include, for each portion,of the plurality of portions, of the image file, storing a portion, ofthe plurality of portions, of the image file in a memory on the clientdevice, generating, while the portion of the image file is in the memoryon the client device, an intermediate hash value for the portion of theimage file, and transferring, based on generating the intermediate hashvalue for the portion of the image file, the portion of the image fileto a storage drive on the client device (block 730). For example, theclient device (e.g., using processor 420, memory 430, storage component440, input component 450, output component 460, communication interface470, and/or the like) may, for each portion, of the plurality ofportions, of the image file, store a portion, of the plurality ofportions, of the image file in a memory on the client device, generate,while the portion of the image file is in the memory on the clientdevice, an intermediate hash value for the portion of the image file,and transfer, based on generating the intermediate hash value for theportion of the image file, the portion of the image file to a storagedrive on the client device, as described above in connection with FIGS.1A-1P.

As further shown in FIG. 7, process 700 may include combining theplurality of portions of the image file, in the storage drive on theclient device, to generate a copy of the image file (block 740). Forexample, the client device (e.g., using processor 420, memory 430,storage component 440, and/or the like) may combine the plurality ofportions of the image file, in the storage drive on the client device,to generate a copy of the image file, as described above in connectionwith FIGS. 1A-1P.

As further shown in FIG. 7, process 700 may include generating, based onthe intermediate hash values for the plurality of portions of the imagefile, a final hash value for the copy of the image file (block 750). Forexample, the client device (e.g., using processor 420, memory 430,and/or the like) may generate, based on the intermediate hash values forthe plurality of portions of the image file, a final hash value for thecopy of the image file, as described above in connection with FIGS.1A-1P.

As further shown in FIG. 7, process 700 may include comparing the finalhash value to an expected hash value for the copy of the image file(block 760). For example, the client device (e.g., using processor 420,memory 430, and/or the like) may compare the final hash value to anexpected hash value for the copy of the image file, as described abovein connection with FIGS. 1A-1P.

As further shown in FIG. 7, process 700 may include storing the copy ofthe image file in an image file store on the client device based ondetermining that the final hash value matches the expected hash value(block 770). For example, the client device (e.g., using processor 420,memory 430, storage component 440, and/or the like) may store the copyof the image file in an image file store on the client device based ondetermining that the final hash value matches the expected hash value,as described above in connection with FIGS. 1A-1P.

Process 700 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, the client device may receive a request toprovide the copy of the image file to another client device on a samesubnet as the client device, and may transmit, based on receiving therequest to provide the copy of the image file, the copy of the imagefile to the other client device.

In some implementations, the client device may receive a wakeinstruction from a master device on a same subnet as the client device,and may transition the client device from an idle state to an activestate based on receiving the wake instruction. In some implementations,the client device, when transmitting the request for the image file, maytransmit the request for the image file based on the client devicetransitioning from the idle state to the active state.

In some implementations, the client device may receive a mapping tableassociated with the image file. In some implementations, the mappingtable for the image file may include information identifying a mappingbetween one or more first portions of the image file and one or moresecond portions of another version of the image file stored on theclient device. In some implementations, the one or more first portionsof the image file may be unchanged from the one or more second portionsof the other version of the image file. In some implementations, theclient device, when combining the plurality of portions of the imagefile, in the storage drive on the client device, may generate the copyof the image file, may combine the plurality of portions of the imagefile with one or more portions of the other version of the image file togenerate the copy of the image file.

In some implementations, the client device may receive a mapping tableassociated with the image file. In some implementations, the mappingtable associated with the image file may include information identifyingone or more portions of the image file that are not included in anotherversion of the image file stored on the client device. In someimplementations, when transmitting the request for the image file, theclient device may transmit, based on the mapping table, a request forthe one or more portions of the image file that are not included in theother version of the image file stored on the client device. In someimplementations, the client device may install a program, from the copyof the image file, onto the client device based on an organizationalrole assigned to the client device.

Although FIG. 7 shows example blocks of process 700, in someimplementations, process 700 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 7. Additionally, or alternatively, two or more of theblocks of process 700 may be performed in parallel.

In this way, imaging platform 330 may store and maintain largequantities of different permutations of the image file in a singleaggregated image file, which reduces the complexity of storing andmaintaining the plurality of permutations of the image file. Moreover,imaging platform 330 may deduplicate the plurality of permutations ofthe image file when generating the aggregated image file so that commonportions of the image file between the plurality of permutations arestored once in the aggregated image. In this way, imaging platform 330reduces the amount of storage resources used to store the aggregatedimage file.

Additionally, in this way, by providing an imaging platform 330 capableof ensuring that a client device 310 managed by imaging platform 330stores the most recent version of an image file by periodicallydetermining whether client device 310 is storing a current version ofthe image file, and transmitting the current version of the image fileto client device 310 based on determining that client device 310 is notstoring the current version of the image file, if client device 310experiences a fault and needs to be recovered or rebuilt, imagingplatform 330 may recover or rebuild client device 310 using the currentversion of the image file stored on client device 310 instead of havingto transmit the current version of the image file to client device 310over a network, which reduces the amount of time it takes to recover orrebuild client device 310, and reduces the amount of time that clientdevice 310 is unusable or offline.

Also, in this way, by determining and dynamically adjusting a bandwidthallocation for transmitting an image file to client device 310 over anetwork based on one or more properties associated with a networkconnection of client device 310, imaging platform 330 may transmit theimage file to the client device in a way that does not adversely affectthe network connection of the client device and/or network connectionsof other client devices 310 in the network, which conserves networkresources and minimizes network latency and/or degradation inperformance of network-provided services.

Furthermore, in this way, a client device 310 may be provided thatreceives a plurality of portions of an image file from imaging platform330 (or from another location), and may generate a plurality ofintermediate hash values, for the plurality of portions, while theplurality of portions is in a memory on the client device. Client device310 may transfer the plurality of portions to a storage drive on clientdevice 310, may generate a copy of the image file, and may generate afinal hash value, for the copy of the image file, from the plurality ofintermediate hash values. In this way, client device 310 may decreasethe amount of time it takes client device 310 to generate a hash valuefor the copy of the image file by generating the plurality ofintermediate hash values for the plurality of the portions of the imagefile, while the plurality of portions of the image file are in thememory on client device 310.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, or the like.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, or the like.A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving an image file atan imaging device; identifying, by the imaging device and based onreceiving the image file, a plurality of organizational roles;distributing, by the imaging device, a copy of the image file and anorganizational role, of the plurality of organizational roles, to eachvirtual machine (VM) of a plurality of VMs; receiving, by the imagingdevice and from a VM of the plurality of VMs, a permutation of the imagefile, based on the organizational role distributed to the VM, from acopy of the image file distributed to the VM; generating, by the imagingdevice, an aggregated image file that includes each permutation of theimage file associated with each organizational role of the plurality oforganizational roles; generating, by the imaging device, a mapping tablefor the aggregated image file, wherein the mapping table includesinformation identifying one or more first portions of a first version ofthe image file that are not included in a second version of the imagefile; determining, by the imaging device and based on identifying theone or more first portions of the first version of the image file, abandwidth allocation; and transmitting, by the imaging device and basedon the bandwidth allocation, the one or more first portions of the firstversion of the image file to a client device, wherein the bandwidthallocation is dynamically adjusted based on client device activity. 2.The method of claim 1, further comprising: identifying an organizationalrole, of the plurality of organizational roles, assigned to the clientdevice; and transmitting, to the client device, an instruction toinstall a permutation of the image file, included in the aggregatedimage file, associated with the organizational role assigned to theclient device.
 3. The method of claim 1, wherein transmitting theaggregated image file to the client device comprises: transmitting theaggregated image file to a plurality of client devices on a same subnet.4. The method of claim 1, wherein transmitting the aggregated image fileto the client device comprises: transmitting the aggregated image fileto a preboot execution environment (PXE) server on a same subnet as theclient device; and transmitting an instruction to the PXE server toprovide the aggregated image file to the client device.
 5. The method ofclaim 1, wherein transmitting the aggregated image file to the clientdevice comprises: providing, to the client device, a notification thatthe aggregated image file is available in an image store; receiving,from the client device and based on the notification, a request for theaggregated image file; and transmitting the aggregated image file to theclient device based on receiving the request.
 6. The method of claim 1,wherein the mapping table for the aggregated image file includesinformation identifying a mapping between one or more first portions ofthe aggregated image file and one or more second portions of anotherversion of the aggregated image file, and wherein the one or more firstportions of the aggregated image file are unchanged from the one or moresecond portions of the other version of the aggregated image file; andfurther comprising: transmitting the aggregated image file to the clientdevice based on the mapping table.
 7. The method of claim 1, furthercomprising: prior to transmitting the aggregated image file to theclient device, detecting that the client device is in an idle state; andtransmitting, to a master device on a same subnet as the client device,an instruction to provide the client device with a wake instructionbased on detecting that the client device is in the idle state.
 8. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors of a device, cause the one or more processors to:receive an image file; identify, based on receiving the image file, aplurality of organizational roles; distribute a copy of the image fileand an organizational role, of the plurality of organizational roles, toeach virtual machine (VM) of a plurality of VMs; receive, from a VM ofthe plurality of VMs, a permutation of the image file, based on theorganizational role distributed to the VM, from a copy of the image filedistributed to the VM; generate an aggregated image file that includeseach permutation of the image file associated with each organizationalrole of the plurality of organizational roles; generating a mappingtable for the aggregated image file, wherein the mapping table includesinformation identifying one or more first portions of a first version ofthe image file that are not included in a second version of the imagefile; determine, based on identifying the one or more first portions ofthe first version of the image file, a bandwidth allocation; andtransmit, based on the bandwidth allocation, the one or more firstportions of the first version of the image file to a client device,wherein the bandwidth allocation is dynamically adjusted based on clientdevice activity.
 9. The non-transitory computer-readable medium of claim8, wherein the one or more instructions, when executed by the one ormore processors, further cause the one or more processors to: identifyan organizational role, of the plurality of organizational roles,assigned to the client device; and transmit, to the client device, aninstruction to install a permutation of the image file, included in theaggregated image file, associated with the organizational role assignedto the client device.
 10. The non-transitory computer-readable medium ofclaim 8, wherein the one or more instructions, that cause the one ormore processors to transmit the aggregated image file to the clientdevice, cause the one or more processors to: transmit the aggregatedimage file to a plurality of client devices on a same subnet.
 11. Thenon-transitory computer-readable medium of claim 8, wherein the one ormore instructions, that cause the one or more processors to transmit theaggregated image file to the client device, cause the one or moreprocessors to: transmit the aggregated image file to a preboot executionenvironment (PXE) server on a same subnet as the client device; andtransmit an instruction to the PXE server to provide the aggregatedimage file to the client device.
 12. The non-transitorycomputer-readable medium of claim 8, wherein the one or moreinstructions, that cause the one or more processors to transmit theaggregated image file to the client device, cause the one or moreprocessors to: provide, to the client device, a notification that theaggregated image file is available in an image store; receive, from theclient device and based on the notification, a request for theaggregated image file; and transmit the aggregated image file to theclient device based on receiving the request.
 13. The non-transitorycomputer-readable medium of claim 8, wherein the mapping table for theaggregated image file includes information identifying a mapping betweenone or more first portions of the aggregated image file and one or moresecond portions of another version of the aggregated image file, andwherein the one or more first portions of the aggregated image file areunchanged from the one or more second portions of the other version ofthe aggregated image file; and wherein the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: transmit the aggregated image file to the clientdevice based on the mapping table.
 14. The non-transitorycomputer-readable medium of claim 8, wherein the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: prior to transmitting the aggregatedimage file to the client device, detect that the client device is in anidle state; and transmit, to a master device on a same subnet as theclient device, an instruction to provide the client device with a wakeinstruction based on detecting that the client device is in the idlestate.
 15. A device, comprising: one or more memories; and one or moreprocessors, communicatively coupled to the one or more memories, to:receive an image file; identify and based on receiving the image file, aplurality of organizational roles; distribute a copy of the image fileand an organizational role, of the plurality of organizational roles, toeach virtual machine (VM) of a plurality of VMs; receive, from a VM ofthe plurality of VMs, a permutation of the image file, based on theorganizational role distributed to the VM, from a copy of the image filedistributed to the VM; generate an aggregated image file that includeseach permutation of the image file associated with each organizationalrole of the plurality of organizational roles; generate a mapping tablefor the aggregated image file, wherein the mapping table includesinformation identifying one or more first portions of a first version ofthe image file that are not included in a second version of the imagefile; determine, based on identifying the one or more first portions ofthe first version of the image file, a bandwidth allocation; andtransmit, based on the bandwidth allocation, the one or more firstportions of the first version of the image file to a client device,wherein the bandwidth allocation is dynamically adjusted based on clientdevice activity.
 16. The device of claim 15, wherein the one or moreprocessors are further to: identify an organizational role, of theplurality of organizational roles, assigned to the client device; andtransmit, to the client device, an instruction to install a permutationof the image file, included in the aggregated image file, associatedwith the organizational role assigned to the client device.
 17. Thedevice of claim 15, wherein the one or more processors, when transmitthe aggregated image file to the client device, are to: transmit theaggregated image file to a plurality of client devices on a same subnet.18. The device of claim 15, wherein the one or more processors, whentransmit the aggregated image file to the client device, are to:transmit the aggregated image file to a preboot execution environment(PXE) server on a same subnet as the client device; and transmit aninstruction to the PXE server to provide the aggregated image file tothe client device.
 19. The device of claim 15, wherein the one or moreprocessors, when transmit the aggregated image file to the clientdevice, are to: provide, to the client device, a notification that theaggregated image file is available in an image store; receive, from theclient device and based on the notification, a request for theaggregated image file; and transmit the aggregated image file to theclient device based on receiving the request.
 20. The device of claim15, wherein the mapping table for the aggregated image file includesinformation identifying a mapping between one or more first portions ofthe aggregated image file and one or more second portions of anotherversion of the aggregated image file, and wherein the one or more firstportions of the aggregated image file are unchanged from the one or moresecond portions of the other version of the aggregated image file; andwherein the one or more processors are further to: transmit theaggregated image file to the client device based on the mapping table.